During dispatching decisions, optimization and access rules may reveal that an ASC cannot access a container's destination location. This happens in the following situations:
The ASC's range does not cover the container's destination location.
Another ASC blocks the destination location.
In these cases, XPS performs the following steps to split a work instruction into two by:
Determining whether the container's destination location lies within or outside the ASC stack, including transfer zones.
Finding an intermediate position (on page 1) for the container based on split decking rules (on page 1).
Generating a new split WI that moves the container from the current location to the new intermediate location.
Sending a dispatch request to ECN4 for the new split WI. In response, ECN4 processes the dispatch request and sets the ASC state in the cache to Dispatched.
Processing the new ASC status from the cache update.
For example, when a gated-in truck confirms the Notify Arrival in the transfer zone with the receival containers planned outside of the landside transfer zone (LSTZ), that is, in the waterside TZ near the ASC, the ASC Optimizer generates split moves: one from the LSTZ to the intermediate location (this move is part of the road queue) and one from the intermediate location to the final destination (this move is part of the housekeeping work queue).